types: fix various use of volatile in type registration
authorChristian Hergert <chergert@redhat.com>
Thu, 19 Nov 2020 03:58:09 +0000 (19:58 -0800)
committerChristian Hergert <chergert@redhat.com>
Thu, 19 Nov 2020 04:21:33 +0000 (20:21 -0800)
commit0d2ea14ac1d0b59588b1bfa60e6e45246496572c
tree0536e92bb86672e6b4981923d44b26bb91e41817
parent7551f85d4cfb0df0cf6adcf882981cc5601288ea
types: fix various use of volatile in type registration

The use of volatile was incorrect in GLib and has been that way for
a long time. Recently however that has changed, and this makes GTK
follow suit to avoid using volatile in the type registration.

See also: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1719

Combined with the above merge request for GLib, this fixes a large
number of compilation warnings when using Clang.
gdk/gdkenumtypes.c.template
gdk/gdkevents.c
gsk/gskdebug.c
gsk/gskenumtypes.c.template
gsk/gskrendernode.c
gsk/gskrendernodeimpl.c
gtk/css/gtkcssenumtypes.c.template
gtk/gtkexpression.c
gtk/gtkprintoperation-win32.c
gtk/gtkprivatetypebuiltins.c.template
gtk/gtktypebuiltins.c.template